home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
BBS Toolkit
/
BBS Toolkit.iso
/
pc_board
/
idxutil2.zip
/
IDX-UTIL.DOC
< prev
Wrap
Text File
|
1992-06-01
|
11KB
|
229 lines
PCB-UTIL.DOC - June 01, 1992 - Gary Meeker
This document contains information on how to use:
IDX-DUPS Version 2.00,
IDX-LIST Version 1.00,
IDX-EDIT Version 1.00, (Still not written)
IDX-DRIV Version 1.00, and
IDX-RSET Version 1.00.
These programs are released as FREEWARE to all REGISTERED PCBoard
Version 14.5 Sysops. The Copyright is retained by Gary Meeker.
What does this mean? If you have purchased a licence for PCBoard V14.5
from Clarke Development, then you are entitled to copy and use these
utilities on as many computers as allowed by your licence from Clark
Development. If you have an illegal copy of PCBoard V14.5, these programs
are not for YOU.
=========================================================================
*DISCLAIMER*DISCLAIMER*DISCLAIMER*DISCLAIMER*DISCLAIMER*DISCLAIMER*
Every effort has been made to avoid error and moderately extensive testing
has been performed on these programs, however, I do not warrant them to be
fit for any purpose or to be free from error and disclaims any liability
for actual or any other damage arising from the use of these programs.
ENSURE YOU KEEP UP-TO-DATE BACKUPS OF ALL YOUR IMPORTANT FILES.
*DISCLAIMER*DISCLAIMER*DISCLAIMER*DISCLAIMER*DISCLAIMER*DISCLAIMER*
=========================================================================
IDX-DUPS Version 2.00 (06/01/92)
List duplicate entries in a PCBoard 14.5(a) File Index. To use type:
IDX-DUPS indexname[.IDX] [indexname2.IDX]] [/Q] [/I] [/Kn]
Where indexfile[.IDX] is the name of the index file to display.
(The .IDX file extension is optional. Do not include the '[' or ']'.)
Optionally you may include an indexname2[.IDX] which will be compared against
the first. Duplicates in the first will still be reported, but any files
found in the second which are also in the first will also be reported.
Duplicates in the second index will only be reported if they are also
in the first.
[/Q] supresses the header info from the output.
[/I] creates a file called COMMON.IDX containing the Index information
from the second Index when a file matches from the first index.
You can include a 3rd IndexfileName to override the default name.
Make sure you don't use the name of a file already on the disk or it
will be overwritten (unless that is what you want.) New with 2.00 is
the ability to use /I with a single IndexFile and get a COMMON.IDX
listing the Duplicates.
[/Kn] Kill Duplicates. n:1=Prompt on all files (default)
2=Prompt on different size files
3=Don't prompt at all (Use with caution)
This feature only works when two .IDX files are specified. The files from
the second .IDX files are the ones that will be deleted. If you have a
CD-ROM, you would want to specify it first and your Hard Disk(s) .IDX file
second, followed by /K (and 1, 2 or 3... If only /K is specified 1 is
assumed).
I setup a CD-Rom conference available to only those Users who contributed
to making the purchase of the CD-Rom Drives & Disks possible. All the
CD-Rom files are available from that conference but not the Main Board
or other Conference Files (accept the Masterfile list Directory.)
I used this to find all the files on my Hard Disks that were also on the
new CD-Roms. I feed DLPATH.LST to MAKEIDX to create an Index for my Hard
Drives. Then using this utility I created an Index of the Duplicates. I
added both of these (one for each CD-Rom) to the DLPATH.LST and deleted
the files from the Hard Drives. This way I didn't loose any files from my
board available to everyone but was able to free up the storage space they
were taking up. My Users could not tell the difference and everyone was
happy. Once IDX-Edit is finished I can add some of the files on the CD-Rom
to these Indexes to help fill out some of the Conferences which are bare
of files right now. I could copy the files from the CD-Rom to the Hard Drives
and create another Index of the Dups to add them in, but it will be easier
after the routine gets finished.
=========================================================================
IDX-List Version 1.00 (01/01/92)
List entries in a PCBoard 14.5(a) File Index. To use type:
IDX-LIST indexname[.IDX] [filemask]
Where indexname[.IDX] is the name of the index file to list.
(The .IDX file extension is optional.)
and [filemask] is the file or wildcard match to list."
=========================================================================
IDX-Edit Version 0.20 (01/01/92) Preliminary Information only.
Edit entries in a PCBoard 14.5(a) File Index. To use type:
IDX-EDIT [indexname[.IDX]
Where indexname[.IDX] is the name of the index file to edit.
(The .IDX file extension is optional.)
If not given, the file name will be prompted for.
This will be the most powerful Utility of the 3 once it is finished. It
will allow for complete editing of the data in the index file. You will
be able to TAG files based on Duplicates, a FileMask or manually. The
Tagged files may then be deleted (or untagged manually). Files will be
able to be inserted also. Plans are also to allow Tagging or Inserting
files by reading a file for Paths\FileNames. Editing of Paths will also
be possible to allow easy changing of drive letters, etc. Paths will be
able to be added or deleted. Other features will be available if I come
up with any or requests are made, and I can work them in.
Currently only Displaying and Editing are finished.
=========================================================================
IDX-DRIV Version 1.00 (06/01/92)
Set Drive Letter on all paths in a PCBoard 14.5(a) File Index. To use type
IDX-DRIV indexname[.IDX] DriveLetter [/Q]
Where indexname[.IDX] is the name of the index file to set.
DriveLetter is the Drive Letter to assign to all paths
[/Q] supresses the header info from the output.
IDX-DRIV is designed to modify the Paths in an IDX file to whatever drive
letter you desire (This is quicker than using MAKEIDX again just because
you changed the drive letter).
=========================================================================
IDX-RSET Version 1.00 (06/01/92)
Set Active CD-Roms and Drives in a PCBoard 14.5(a) File Indexes. To use type
IDX-RSET ConfigFile [/Q]"
Where: ConfigFile = Drive:Path to our configuration file.
[/Q] supresses the header info from the output.
The ConfigFile contains 4 or more lines:
Line 1: Loc/Name of the CDROM database File
Line 2: Place CD-ROM Index Files at Beginning of DLPATH.LST files.
Line 3: Number of DLPATH.LST files to check
Line 4+ Loc/Name of each DLPATH.LST file to be checked/altered
The CDROM database File contains 3 or more lines
Line 1: Number of CD-ROMS listed in database, List of Drives for CD-ROMS
Line 2+ CDRom Name Label, Loc/Name of IndexFile, TestFile
IDX-RSET is designed to assist in changing CD-ROMS if you have more CD-ROMS
than drives. First create an Index file for each CD-ROM using MAKEIDX. Next
create the CDROM DataBase file using a text editor. Line 1 defines how many
CD-ROMS will be listed in the data base and a list of CD-ROM Drive letters
with no spaces or seperators (ie. STU or STUVWX). The following lines include
a label for identifying the CD-ROM (used only as output name for your use)
(but NOTE: DO NOT include a comma in the label)), the Drive:\Path\Filename
of the indexfile for this CD-ROM, and a test file unique to this CD-ROM to
allow the program to identify the CD-ROM (DO NOT include a drive letter or
leading :\ for the path.)
Example (I have 2 CD-ROMS and 1 Drive)
2,S
CD-Rom1, H:\IDX-ROM1.IDX, ROM01\1603.ZIP
CD-Rom2, H:\IDX-ROM2.IDX, ROM201\ALTBRN12.ZIP
Next create the config file using a text editor. The first line contains
the Drive:\Path\Filename of the above database. The second line determines
if the CD-ROM Index files should be listed at the beginning (YES) or the
end (NO) of the DLPATH.LST files (NOTE: a special mode is available by the
use of AUTO which causes the Index files to be listed after the end of the
first occurances of INDEX files in the DLPATH.LST file). The third Line
contains the number of DLPATH.LST files to be checked. The following lines
contain the Drive:\PATH\Filenames of each of the DLPATH.LST files.
When run, IDX-RSET will Check each CD-ROM listed and determine which drive
it is in. It will then modify the INDEX file so the PATHS will contain the
proper Drive letter. Once each CD-ROM is located it will read each of the
DLPATH.LST files listed and look for INDEX files. If the Index File is one
of the files listed, it will be skipped. Any other INDEX file as well as any
other line will be copied to the new DLPATH.LST file which will then be
renamed to the origional file. The result will be a DLPATH.LST file which will
contain the proper index files for the CD-ROMS that are found to be online
and the index files modified so the paths contain the proper Drive letter.
=========================================================================
CONTACTING THE AUTHOR
There are a number of ways to contact the author:
1. Call the support BBS, SHARP Technical Support Line BBS (404) 962-1788.
2. Fax: (404) 995-0613
3. Send net mail message through one of the mail networks in a CD-Rom
Sysops, PCBoard, QuickBasic or TeleMate Conference addressed to 'Gary Meeker'.
Available networks are Intelec, Rime, ILink and P/Net. Although I sometimes
do not get on the networks for a couple months at a time, so my BBS or P/NET
which I do carry on my BBS is the quickest bet.
4. Send letter through regular post to the following address:
ATTN: Gary Meeker
SHARP Technical Support Line BBS
725-C Old Norcross Road
Lawrenceville, GA 30245
=========================================================================
Source Code:
All programs are written in QuickBasic 4.5 and compiled using P.D.Q.
from Crescent Software. This results in very small code. Also several
routines from Crescent's QuickPack Professional Library and some of myown
Library routines were used.
For those who would like source code, it can be obtained by sending $10
to the address above, made payable to Gary Meeker. Specify 3.5" or 5.25" &
DD or HD format disks. You will receive the QB4.5 source code and the
assembly code and Library for myown routines. To compile the code you will
need P.D.Q. & QuickPack Professional from Crescent Software or replace the
Library calls by uncommenting the internal routines which accomplish the
same functions but result in larger code. Compiling then can be done under
QB4.5 just fine. (although the files will be 2 to 4 times as large.)
=========================================================================